vm: implement case string
in bytecode
#1148
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Remove the dedicated
string
slice-list matching support from the VMand replace it with an in-bytecode implementation. This gives more
control to the code generator and removes the last internal usage of
cnstString
, preparing for the latter's removal.Details
An
of
branch of acase
matching over a string is now translatedinto a sequence of
LdConst
+EqStr
+TJmp
(one per label),replicating the behaviour previously implemented by the
Branch
opcode.
While the bytecode implementation is a bit slower and also results in
slightly larger VM executables, having less high-level string operations
in the VM makes it easier to evolve.
The string slice-list matching is removed from the
Branch
opcodeimplementation, and
cnstSliceListStr
together with all its usages isremoved.